Information processing device, information processing method, information processing program, and recording medium

ABSTRACT

In an information processing device adapted for performing an application program, a displaying unit causes a display device to display information related to a state transition of the application program. A generation unit receives an input updating request for updating information related to a displayed state transition, and generates an application program which realizes a state transition according to the updating request.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to an information processing device whichis inclusive of a computer device, such as a personal computer or servercomputer, and an image forming device, such as a copier, printer,scanner, facsimile, composite machine or multi-function peripheral.Moreover, the present invention relates to an information processingmethod, an information processing program, and a recording medium, suchas an SD memory card.

2. Description of the Related Art

In recent years, a composite machine or multi-function peripheral whichis provided with a copier function, a printer function, a scannerfunction and a facsimile function has come to be marketed. The compositemachine or multi-function peripheral is configured to print an image ona copy sheet when it functions as a copier or a printer. The compositemachine or multi-function peripheral is configured to read an image froman original document when it functions as a copier or a scanner. Thecomposite machine or multi-function peripheral is configured to transmitan image to or receive an image from an external device through acommunication line when it functions as a facsimile. For example, seeJapanese Laid-Open Patent Application No. 2002-084383.

In recent years, various application programs are often implemented inthe composite machine or the multi-function peripheral. However, it isnot unusual that a user of the composite machine or the multi-functionperipheral does not notice existence of a special useful applicationprogram implemented therein.

In such a case, existence of the special useful application program willbecome useless, and an unnecessary burden will be continuously put onthe user of the composite machine or the multi-function peripheral. Suchsituations are the same also with respect to information processingdevices other than image forming devices, such as composite machines ormulti-function peripherals.

SUMMARY OF THE INVENTION

According to one aspect of the invention, there is provided an improvedinformation processing device and method in which the above-describedproblems are eliminated.

According to one aspect of the invention there is provided aninformation processing device which provides a user of the informationprocessing device with a useful application program in the informationprocessing device in which various applications are implemented.

In an embodiment of the invention which solves or reduces one or more ofthe above-mentioned problems, there is provided an informationprocessing device adapted for performing an application program, theinformation processing device comprising: a displaying unit causing adisplay device to display information related to a state transition ofthe application program; and a generation unit receiving an inputupdating request for updating information related to a displayed statetransition, and generating an application program which realizes a statetransition according to the updating request.

In an embodiment of the invention which solves or reduces one or more ofthe above-mentioned problems, there is provided any of an informationprocessing method, a computer-readable program, and a computer-readablerecording medium which are adapted for providing a user of theabove-mentioned information processing device with a useful applicationprogram in the information processing device in which variousapplications are implemented.

According to embodiments of the information processing device and methodof the invention, it is possible to provide the technique of providingthe user of the information processing device with a useful applicationprogram for use in the information processing device in which variousapplication programs are implemented.

BRIEF DESCRIPTION OF THE DRAWINGS

Other objects, features and advantages of the present invention will beapparent from the following detailed description when reading inconjunction with the accompanying drawings.

FIG. 1 is a diagram showing the composition of a multi-functionperipheral in an embodiment of the invention.

FIG. 2 is a diagram showing the hardware composition of themulti-function peripheral of FIG. 1.

FIG. 3 is a diagram showing the external appearance of themulti-function peripheral of FIG. 1.

FIG. 4 is a diagram showing the composition of an operation panel in themulti-function peripheral of FIG. 1.

FIG. 5 is a functional block diagram for explaining operation of acollector.

FIG. 6 is a state transition diagram for explaining a state transitionof the multi-function peripheral of FIG. 1.

FIG. 7 is a state transition diagram for explaining a state transitionof the multi-function peripheral of FIG. 1.

FIG. 8 is a state transition diagram for explaining a state transitionof the multi-function peripheral of FIG. 1.

FIG. 9 is a state transition diagram for explaining a state transitionof the multi-function peripheral of FIG. 1.

FIG. 10 is a state transition diagram for explaining a state transitionof the multi-function peripheral of FIG. 1.

FIG. 11 is a state transition diagram for explaining a state transitionof the multi-function peripheral of FIG. 1.

FIG. 12 is a state transition diagram for explaining a state transitionof the multi-function peripheral of FIG. 1.

FIG. 13 is a diagram for explaining a framework and a class library.

FIG. 14 is a flowchart for explaining a detection processing of JSDKapplication.

FIG. 15 is a flowchart for explaining a generation processing of JSDKapplication.

FIG. 16 is a diagram showing an example of an application statetransition display screen.

FIG. 17 is a diagram showing an example of the application statetransition display screen in the edit mode.

FIG. 18 is a diagram showing an example of a state edit display.

FIG. 19 is a diagram showing an example of a transition conditionsetting display screen.

FIG. 20 is a diagram showing an example of the application statetransition display screen where the edit result is reflected.

FIG. 21 is a diagram showing an example of a state transition displayscreen of a functional module.

FIG. 22 is a diagram showing an example of the state edit display screenwhich is related to the state of a functional module.

FIG. 23 is a diagram showing an example of a transition conditionsetting display screen which is related to the internal state transitionof a functional module.

FIG. 24 is a diagram showing an example of a detailed informationsetting display screen.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

A description will be given of embodiments of the invention withreference to the accompanying drawings.

FIG. 1 shows the composition of the multi-function peripheral (MFP) 101in an embodiment of the invention.

The MFP 101 of FIG. 1 comprises various hardware elements 111, varioussoftware elements 112, and a MFP booting unit 113. The hardware elements111 of the multi-function peripheral 101 include an image pick-up unit121, a printing unit 122, and other hardware elements 123.

The image pick-up unit 121 is the hardware for reading an image (imagedata) from the original document. The printing unit 122 is the hardwarefor printing an image (image data) on a copy sheet.

The software elements 112 of the multi-function peripheral 101 includevarious application programs 131 and various platform programs 132. TheOS (operating system), such as UNIX (registered trademark), carries outparallel execution of the respective programs of the software elements112 as the processes.

The application programs 131 include a copy application 141 which is theapplication program for a copier, a printer application 142 which is theapplication program for a printer, a scanner application 143 which isthe application program for a scanner, a facsimile application 144 whichis the application program for a facsimile, a network file application145 which is the application program for network files.

Another one of the application programs 131 can be developed using adedicated SDK (software-development kit). Such application program 131which is developed using the SDK will be called SDK application. Thededicated SDK may include a CSDK for developing the application program131 in the C language, and a SDK for developing the application program131 in the Java (registered trademark) language. The application program131 developed using the CSDK will be called “CSDK application”, and theapplication program 131 developed using the JSDK is called “JSDKapplication”.

The multi-function peripheral 101 of FIG. 1 includes also the CSDKapplication 146 and the JSDK application 147. Moreover, the JSDKplatform 148 is further provided in the multi-function peripheral 101 ofFIG. 1 as the software element 112 which performs the intermediary tasksbetween the JSDK application 147 described in the Java language andanother software element 112 described in the C language.

The platform 132 includes various control services 151, a systemresource manager 152, and various handlers 153. The control services 151include a network control service (NCS) 161, a facsimile control service(FCS) 162, a delivery control service (DCS) 163, an engine controlservice (ECS) 164, a memory control service (MCS) 165, an operationpanel control service (OCS) 166, a certification control service (CCS)167, a user directory control service (UCS) 168, and a system controlservice (SCS) 169. The handlers 153 include a facsimile control unithandler (FCUH) 171 and an image memory handler (IMH) 172.

The process of NCS 161 performs intermediary tasks for networkcommunications. The process of FCS 162 provides the API (applicationprogram interface) of facsimile. The process of DCS 163 performs controlrelated to the message distribution processing of stored documents. Theprocess of ECS 164 performs control related to the image pick-up unit121 and the printing unit 122. The process of MCS 165 performs controlrelated to the memory and the hard disk drive. The process of OCS 166performs control related to the operation panel. The process of CCS 167performs control related to authenticating processing and chargingprocessing. The process of UCS 168 performs control related to themanagement of user information. The process of SCS 169 performs controlrelated to the management of the system.

A virtual application service (VAS) 135 is provided as the softwareelement 112 which performs the intermediary tasks between theapplication program 131 and the platform 132. The VAS 135 operates as aserver process which makes the application program 131 a client, whileit operates as a client process which makes the platform 132 a server.The VAS 135 is provided with the wrapping function which serves toconceal the platform 132 from the application program 131, and it playsthe role which absorbs the version difference accompanied with theupgrading of the platform 132.

The MFP booting unit 113 is first initiated upon the power up of themulti-function peripheral 101. Thereby, the OS, such as UNIX (registeredtrademark), is started and the application programs 131 and the platform132 are started. These programs are stored in the hard disk drive or thememory card, and they are read from the hard disk drive or the memorycard and loaded to the computer memory.

FIG. 2 is a diagram showing the hardware composition of themulti-function peripheral 101 of FIG. 1. The hardware elements 111 ofthe multi-function peripheral 101 include a controller 201, an operationpanel 202, a facsimile control unit (FCU) 203, the image pick-up unit121, and the printing unit 122.

The controller 201 comprises a CPU 211, an ASIC 212, a NB 221, a SB 222,a MEM-P 231, a MEM-C 232, a HDD (hard disk drive) 233, a memory cardslot 234, a NIC (network interface controller) 241, a USB device 242, anIEEE1394 device 243, and a Centronics device 244.

The CPU 211 is the IC for various information processing. The ASIC 212is the IC for various image processing. The NB 221 is the north bridgeof the controller 201. The SB 222 is the south bridge of the controller201. The MEM-P 231 is the system memory of the multi-function peripheral101. The MEM-C 232 is the local memory of the multi-function peripheral101. The HDD 233 is the storage device of the multi-function peripheral101. The memory card slot 234 is a slot for setting a memory card 235.The NIC 241 is a controller for network communications by using a MACaddress. The USB device 242 is a device for providing the connectioninterface in conformity with the USB specifications. The IEEE1394 device243 is a device for providing the connection interface in conformitywith the IEEE1394 specifications. The Centronics device 244 is a devicefor providing the connection interface in conformity with the Centronicsspecifications.

The operation panel 202 is the hardware (operation device) for anoperator to give an input to the multi-function peripheral 101, while itis the hardware (display device) for an operator to obtain an outputfrom the multi-function peripheral 101.

FIG. 3 is a diagram showing the external appearance of themulti-function peripheral 101 of FIG. 1.

In FIG. 3, the position of the image pick-up unit 121, the position ofthe printing unit 122, and the position of the operation panel 202 areillustrated. Illustrated further in FIG. 3 are a document set part 301used as the place of an original document being set, a sheet feedingpart 302 used as the place of a copy sheet being fed, and a sheetejection part 303 used as the place of a copy sheet being ejected.

The operation panel 202 comprises a touch panel 311, ten keys 312, astart button 313, a reset button 314, function keys 315, and aninitial-setting button 316 as shown in FIG. 4. The touch panel 311 isthe hardware (touch operation unit) for giving an input to the MFP bytouch operation, while it is the hardware (display device) for obtainingan output from the MFP in the form of a display screen. The ten keys 312are the hardware for giving a numeric input by key (button) operation.The start button 313 is the hardware for performing start operation bydepression of the button. The reset button 314 is the hardware forperforming reset operation by depression of the button. The functionkeys 315 are the hardware for displaying an operational screen by CSDKapplication 146 or JSDK application 147 by depression of the key(button). The initial-setting button 316 is the hardware for displayingan initial-setting screen by depression of the button.

The document set part 301 contains an ADF (automatic document feeder)321, a flat bed 322, and a flat bed cover 323. The sheet feeding part302 contains four sheet trays. The sheet ejection part 303 contains asheet ejection tray.

FIG. 5 is a functional block diagram for explaining operation of acollector 401. The collector 401 is one of a plurality of JSDKapplications 147 implemented in the multi-function peripheral 101 ofFIG. 1. The collector 401 collects various kinds of information relatedto the operating condition of the multi-function peripheral 101 of FIG.1, and performs various information processing related to JSDKapplication 147 of the multi-function peripheral 101 of FIG. 1.

As shown in FIG. 5, the collector 401 comprises an informationcollecting unit 411, an information acquisition unit 412, an applicationdetecting unit 413, an application generation unit 414, and anapplication notification unit 415. The information collecting unit 411is a functional block which collects automatically information relatedto an operating condition of the multi-function peripheral 101. Theinformation acquisition unit 412 is a functional block which acquiresautomatically information related to a state transition of themulti-function peripheral 101. The application detecting unit 413 is afunctional block which detects automatically a recommended JSDKapplication 147 for use in the multi-function peripheral 101. Theapplication generation unit 414 is a functional block which generatesautomatically a recommended JSDK application 147 for use in themulti-function peripheral 101. The application notification unit 415 isa functional block which notifies automatically a user of existence ofthe recommended JSDK application 147 for use in the multi-functionperipheral 101.

FIG. 6, FIG. 7 and FIG. 8 are state transition diagrams for explainingstate transitions of the multi-function peripheral 101 of FIG. 1,respectively.

The state transition diagram of FIG. 6 illustrates the case in which auser specifies the destination address and transmits the scanning resultby e-mail.

First, if the user turns ON the power supply of the multi-functionperipheral 101, the multi-function peripheral 101 shifts to theauthentication state 501 (S1). Next, if the user gives a login to themulti-function peripheral 101, the multi-function peripheral 101 shiftsto the function selection state 502 (S2).

Next, if the user chooses the scanning function, the multi-functionperipheral 101 shifts to the scan state 503 (S3). Next, if the usercompletes the scan operation, the multi-function peripheral 101 returnsto the function selection state 502 (S4). Next, if the user chooses theaddress function, the multi-function peripheral 101 shifts to theaddress state 504 (S5). Next, if the user completes the addressoperation, the multi-function peripheral 101 returns to the functionselection state 502 (S6). Next, if the user chooses the electronic mailfunction, the multi-function peripheral 101 shifts to the e-mail state505 (S7). Next, if the user completes the e-mail transmission operation,the multi-function peripheral 101 returns to the function selectionstate 502 (S8).

In the collector 401, the information collecting unit 411 collectsinformation related to an operating condition of the multi-functionperipheral 101. This information is, for example, log informationindicating which user uses the multi-function peripheral 101, whatfunction thereof, by what setting, and at what date and time, etc.

In the collector 401, the information acquisition unit 412 acquiresinformation related to a state transition of the multi-functionperipheral 101, by using the information collected by the informationcollecting unit 411. This information is, for example, historyinformation indicating how the state of the multi-function peripheral101 has changed from S1 to S8. By obtaining the history information, thecollector 401 is able to recognize the processes of the statetransitions of the multi-function peripheral 101.

When the operating condition of the multi-function peripheral 101 ofFIG. 1 is frequently set in the case in which the user specifies thedestination address and transmits the scanning result by e-mail, thefrequency of occurrence of the state transitions “S3-S4-S5-S6-S7-S8” ofFIG. 6 is high with respect to the state transition of themulti-function peripheral 101 of FIG. 1. Therefore, as shown in thestate transition of FIG. 7, if a state transition (SX) from the scanstate 503 to the address state 504 and a state transition (SY) from theaddress state 504 to the e-mail state 505 can be performed, such is veryconvenient for the user. These are equivalent to a transition of theoperation display screen from the scanning display screen directly tothe address setting display screen after the completion of the scanoperation, and a transition of the operation display screen from theaddress setting display screen directly to the e-mail transmissiondisplay screen after the completion of the address setting operation.

Suppose that the multi-function peripheral 101 of FIG. 1 is providedwith a JSDK application 147 which realizes the state transitions“SV-SW-SX-SY-SZ” of FIG. 8. This JSDK application 147 is a useful JSDKapplication 147 that realizes the state transitions of FIG. 7,considering the above-mentioned viewpoint. Existence of such JSDKapplication 147 can be detected by using the information related to thestate transition of the multi-function peripheral 101 of FIG. 1.

For this purpose, in the collector 401, the application detecting unit413 uses the information acquired by the information acquisition unit412 (which information corresponds to the information collected by theinformation collecting unit 411), and detects existence of such JSDKapplication 147 as being the recommended JSDK application 147 for use inthe multi-function peripheral 101. The details of this detecting methodwill be described later.

Moreover, in the collector 401, the application notification unit 415notifies a user of existence of the JSDK application 147 detected by theapplication detecting unit 413, as the recommenced JSDK application 147for use in the multi-function peripheral 101. The details of thisnotifying method will be described later.

For example, a case in which a scanning result is transmitted by e-mailand the same is transmitted by facsimile is considered. In the addressstate 504, after the state transitions of S1-S5 of FIG. 6 are performed,the user inputs a mail address together a FAX number as the addresssetting operation. Alternatively, the address setting operation may beselection of a user name of a user as the destination, instead of thedirect input of the mail address and the FAX number. In this case, whatis necessary is just to set up a transmission destination appropriatefor every individual user.

Some users are registered with their mail addresses as the transmissiondestinations, and other users are registered as the transmissiondestinations with their FAX numbers, or with both the FAX numbers andthe mail addresses.

If the address setting operation is completed, the multi-functionperipheral 101 returns to the function selection state 502 (S6). Next,if the user chooses the electronic mail function, the multi-functionperipheral 101 shifts to the e-mail state 505 (S7). Next, if the usercompletes the e-mail transmission operation, the multi-functionperipheral 101 returns to the function selection state 502 (S8) If theuser chooses the facsimile function, the multi-function peripheral 101shifts to the facsimile state 506 (S9). If the FAX transmission iscompleted, the multi-function peripheral 101 returns to the functionselection state (S10).

When the operating condition of the multi-function peripheral 101 isfrequently set into the case in which the user specifies the destinationaddress and transmits the scanning result by both the e-mailtransmission and the FAX transmission, the frequency of occurrence ofthe state transitions “S3-S4-S5-S6-S7-S8-S9-S10” of FIG. 6 is high withrespect to the state transition of the multi-function peripheral 101.

In this case, in the collector 401, the application detecting unit 413uses the information acquired by the information acquisition unit 412,and detects existence of a JSDK application 147 which realizes the statetransitions like “SV-SW-SX-SY-SZ-SY′-SZ′” shown in FIG. 9 as being arecommended JSDK application 147 for use in the multi-functionperipheral 101.

Moreover, a case in which the user transmits a scanning result by e-mailand performs printing of the same is considered. In the functionselection state 502, after the state transitions of S1-S8 of FIG. 6 areperformed, the user chooses the print function by making the scanningresult into a printing object. According to the user's selection, themulti-function peripheral 101 shifts to the print state 507 (S11). Ifthe user completes the printing of the scanning result, themulti-function peripheral 101 shifts to the function selection state(S12).

When the operating condition of the multi-function peripheral 101 isfrequently set into the case in which the user transmits the scanningresult by e-mail and performs the printing of the scanning result, thefrequency of occurrence of the state transitions“S3-S4-S5-S6-S7-S8-S11-S12” of FIG. 6 is high with respect to the statetransition of the multi-function peripheral 101.

In this case, in the collector 401, the application detecting unit 413uses the information acquired by the information acquisition unit 412,and detects existence of a JSDK application 147 which realizes the statetransitions like “SV-SW-SX-SY-SZ-SZ′′” shown in FIG. 10, as being arecommended JSDK application 147 for use in the multi-functionperipheral 101.

Moreover, a case in which the user transmits a scanning result by e-mailand performs printing of a destination address for checking of thedestination address is considered. In the function selection state 502,after the state transitions of S1-S8 of FIG. 6 mentioned above areperformed, the user chooses the print function by making the address(transmission history) of the transmission destination of the scanningresult into a printing object. According to the user's selection, themulti-function peripheral 101 shifts to the print state 507 (S11). Ifthe user completes the printing of the transmission destination address,the multi-function peripheral 101 returns to the function selectionstate (S12).

Thus, when the operating condition of the multi-function peripheral 101is frequently set into the case in which the user transmits the scanningresult by e-mail and prints the transmission destination address of thescanning result, the frequency of occurrence of the state transitions“S3-S4-S5-S6-S7-S8-S11-S12” of FIG. 6 is high with respect to the statetransition of the multi-function peripheral 101.

In this case, in the collector 401, the application detecting unit 413uses the information acquired by the information acquisition unit 412,and detect existence of a JSDK application 147 which realizes the statetransitions like “SV-SW-SX-SY-SZ-SY′′” shown in FIG. 11, as being arecommended JSDK application 147 for use in the multi-functionperipheral 101.

When the address functional module which realizes the address state 504is updated to the enhanced version which has the print function ofprinting a transmission destination address, the application detectingunit 413 of the collector 401 detects existence of a JSDK application147 which realizes the state transitions like “SV-SW-SX-SY-SZ-Sx-Sy”shown in FIG. 12, as being a recommended JSDK application 147 for use inthe multi-function peripheral 101.

In FIG. 12, the state transition Sx (x: lower-case character) denotes atransition from the address state 504 within the address function moduleto the address print state (address print) 504′, and the statetransition Sy (y: lower-case character) denotes a transition or returnfrom the address print state within the address function module.

Next, the details of the collection method of log information and theacquisition method of history information will be explained.

Suppose that the log information is collected with the function levelsof the multi-function peripheral 101. The log information indicates anyof the use of the electronic mail function, the use of the addressfunction, the use of the print function, the use of the facsimilefunction, the use of the copy function, and the use of the scanningfunction.

The application programs 131 implemented in the multi-functionperipheral 101 are created based on the classes (functional modules) ofthe functional levels of the multi-function peripheral 101. There arevarious classes including a class (scanning function module) related tothe scan state 503, a class (address functional module) related to theaddress state 504, a class (electronic mail function module) related tothe e-mail state 505, etc.

This makes it easier to acquire the history information related to thestate transitions of the multi-function peripheral 101 on the basis ofthe functional level (functional module unit) of the multi-functionperipheral 101. Moreover, this makes it easier to detect which JSDKapplication 147 has the ability to perform a specific state transition,and detect what kind of state transition a specific JSDK application 147has, on the basis of the functional level (functional module unit) ofthe multi-function peripheral 101.

The details of the detecting method of JSDK application 147 will beexplained. The JSDK applications 147 to be detected may be either theinstalled ones which are contained the HDD 233 or the memory card 235 ofthe multi-function peripheral 101, or the non-installed ones which existin the media inserted in the multi-function peripheral 101 or in thenetwork to which the multi-function peripheral 101 is connected.

The collector 401 collects periodically and automatically theinformation related to the JSDK applications 147 from the HDD 233, thememory card 235, the media, or the network. And the collector 401accumulates into a database the collected application informationrelated to the JSDK applications 147 being detected, and manages thedatabase.

The information related to the state transition of each JSDK application147 is also registered into the application information. Therefore, theapplication detecting unit 413 detects a recommended JSDK application147 for use in the MFP, as a result of comparing the information relatedto the state transition of the multi-function peripheral 101 collectedby the information collecting unit 411, with the information related tothe state transition of each JSDK application 147 in the database.

The details of the notifying method of JSDK application 147 will beexplained. Existence of the detected JSDK application 147 is notified toa user by displaying it on the banner area of the operation displayscreen currently displayed on the touch panel 311 of the multi-functionperipheral 101.

When the detected JSDK application 147 is the non-installed one,existence of the detected JSDK application 147 may be notified to theuser regardless of whether the notification is performed before or afterit is installed. Installation of the JSDK application 147 which isnotified before it is installed will be carried out by the user'sdepression operation of the banner area as a trigger.

The collector 401 of the multi-function peripheral 101 of FIG. 1 usesthe information related to the state transition of the multi-functionperipheral 101 (which information corresponds to the information relatedthe operating condition of the multi-function peripheral 101), detects arecommended JSDK application 147 for use in the multi-functionperipheral 101, and notifies a user of existence of the recommended JSDKapplication 147.

The use mode as to how the multi-function peripheral 101 has been usedwill be reflected in the results of the detection of the JSDKapplication 147. Thus, the collector 401 of the multi-functionperipheral 101 of FIG. 1 can provide the user with useful JSDKapplication 147.

The collector 401 uses the information related to the operatingcondition of the multi-function peripheral 101 or the informationrelated to the state transition thereof, on a user basis (or for everyindividual user), and detects existence of a recommended JSDKapplication 147 for use in the multi-function peripheral 101 on a userbasis, and notifies the user of the detection result. Since theindividuality for every user is reflected in the use mode as to how themulti-function peripheral 101 has been used, and therefore it is moreconvenient to reflect the characteristics of every user in therecommendation of JSDK application 147 for use in the MFP.

Each user is managed by using a user ID. For example, JSDK application147 “A” is recommended to the user “Mr. Suzuki” who has the user ID“001”, JSDK application 147 “B” is recommended to the user “Mr. Sato”who has the user ID “002”, and JSDK application 147 “C” is recommendedto the user “Mr. Okubo” who has the user ID “003”. If the multi-functionperipheral 101 is provided so that the login processing is not carriedout by the users, it is sufficient that existence of a recommended JSDKapplication 147 for use in the multi-function peripheral 101 is detectedon a device basis, not on a user basis.

The application generation unit 414 in the collector 401 may beconfigured to generate a recommended JSDK application 147 for use in themulti-function peripheral 101, by using the information acquired by theinformation collecting unit 411 and the information acquisition unit412, instead of detecting of the recommended JSDK application 147 by theapplication detecting unit 413. According to this configuration, it isunnecessary to prepare the recommended JSDK application 147, and, evenwhen the recommended JSDK application 147 does not exist in the MFP, itis possible to take the corrective measure in such a case.

The details of the generating method of JSDK application 147 will beexplained. The collector 401 generates a JSDK application 147 from thestate transition diagram as shown in FIG. 8. The state transitiondiagram of FIG. 8 can be generated from the log information or thehistory information. The programming language of the JSDK application147 being generated is the Java (registered trademark). It may beconfigured to generate the software of XML based on XMI like an UMLdrawing tool.

Moreover, the multi-function peripheral 101 of FIG. 1 is provided withthe framework and the class library for facilitating generation of JSDKapplication 147 as shown in FIG. 13. The framework is a half-completionsoftware element used as the base of JSDK application 147, and itprovides the upper layer of JSDK application 147. The class library is alibrary of the classes used as the parts of JSDK application 147, and itprovides the lower layer of JSDK application 147.

As shown in FIG. 13, the framework comprises a logic framework and auser-interface framework. The logic framework is a logic-relatedframework of JSDK application 147, and it specifies a state transitionof the multi-function peripheral 101. The user-interface framework is auser-interface-related framework of JSDK application 147, and itspecifies a display-screen transition of the multi-function peripheral101.

As shown in FIG. 13, the class library comprises a copy class which is acopy-related class, a printer class which is a printer-related class, ascanner class which is a scanner-related class, a facsimile class whichis a facsimile-related class, an operation panel class which is anoperation-panel-related class, and a network class which is anetwork-related class.

It may be configured so that a user or a super-user is allowed tocorrect the generated JSDK application 147. Concerning the generatingmethod of JSDK application 147, Japanese Patent Application No.2004-062413 discloses a similar generating method of JSDK application.

Information related to a state transition of JSDK application 147generated by the application generation unit 414, is included in theapplication information to form the database, and it is registered intothe database.

FIG. 14 is a flowchart for explaining the detection processing of JSDKapplication 147, which is performed by the collector 401.

As shown in FIG. 14, the collector 401 collects the log informationrelated to the operating condition of the multi-function peripheral 101(S101). The collector 401 acquires the history information related tothe state transition of the multi-function peripheral 101 (S102).

The collecting processing of the log information and the acquiringprocessing of the history information may be performed each time a giventime is reached, or each time the period of a predetermined time haspassed, or each time a predetermined operation is carried out.

Next, the collector 401 detects a recommended JSDK application 147 foruse in the multi-function peripheral 101 (S103). The collector 401notifies a user of existence of the recommended JSDK application 147 foruse in the multi-function peripheral 101 (S104). For example, thedetection processing of JSDK application 147 is performed such that,when the frequency of occurrence of a specific state transition reachesa predetermined threshold, the JSDK application 147 which realizes thespecific state transition is detected. For example, the notificationprocessing of JSDK application 147 is performed immediately after thedetection processing of JSDK application 147 is done. Since the touchpanel 311 of the multi-function peripheral 101 is occupied by any of theapplication programs 131 in principle, the notification processing ofJSDK application 147 is performed through such application program 131.

FIG. 15 is a flowchart for explaining the generation processing of JSDKapplication 147, which is performed by the collector 401.

As shown in FIG. 15, the collector 401 collects the log informationrelated to the operating condition of the multi-function peripheral 101(S201). The collector 401 acquires the history information related tothe state transition of the multi-function peripheral 101 (S202).

The collecting processing of the log information and the acquiringprocessing of the history information may be performed each time a giventime is reached, or each time the period of a predetermined time haspassed, or each time a predetermined operation is carried out.

Next, the application generation unit 414 of the collector 401 generatesa recommended JSDK application 147 for use in the multi-functionperipheral 101 (S203). The application notification unit 415 notifies auser of existence of the recommended JSDK application 147 for use in themulti-function peripheral 101 (S204)

For example, the generation processing of JSDK application 147 at thestep S203 is performed when the frequency of occurrence of a specificstate transition reaches a predetermined threshold, so that a JSDKapplication 147 which realizes the specific state transition isgenerated. For example, the notification processing of the JSDKapplication 147 at the step S204 is performed immediately after thegeneration processing of the JSDK application 147 is performed.

Since the touch panel 311 of the multi-function peripheral 101 normallyis occupied by any of the application programs 131, the notificationprocessing of the JSDK application 147 is performed through thecorresponding application program 131.

In the above-described embodiment, the example in which the applicationgeneration unit 414 generates automatically a JSDK application 147 whichrealizes the state transition, based on the history information relatedto the state transition of the multi-function peripheral 101 has beendescribed. However, the generation processing of JSDK application 147 inthe multi-function peripheral 101 is not limited to this embodiment.Alternatively, the generation processing of JSDK application 147 may beconfigured such that the user edits the state transition of the JSDKapplication 147 detected by the application detecting unit 413 is editedby the user interactively, and a new JSDK application 147 is generated.

For example, if the application detecting unit 413 detects existence ofa recommended JSDK application 147 for use in the multi-functionperipheral 101, by using the information related to the state transitionof the multi-function peripheral 101, the application detecting unit 413displays that information on the banner area of the operation screen,currently displayed on the touch panel 311 of the multi-functionperipheral 101. A button for displaying the information related to thestate transition of the detected JSDK application 147 is displayed onthe banner area. If the user depresses the button on the banner area,then the application notification unit 415 displays on the touch panel311 the screen in the information related to the state transition of theJSDK application 147 is displayed (which screen will be called theapplication state transition display screen).

FIG. 16 is a diagram showing an example of the application statetransition display screen.

As shown in FIG. 16, the application state transition display screen 500comprises an application-name indicating area 510, an edit button 520, aclose button 530, and a state-transition indicating area 540.

The application-name indicating area 510 is an area where theapplication name of the JSDK application 147 (which will be called thecurrent application) whose information related to the state transitionis to be displayed.

The state-transition indicating area 540 is an area where theinformation related to the state transition of the current applicationis displayed. In the state-transition indicating area 540, the buttons(which will be called the state buttons) which correspond to respectivestates of the current application are arranged in order of the statetransitions. In the state-transition indicating area 540 of FIG. 16, thestate transitions concerning the state transition diagram shown in FIG.8 are displayed.

That is, the current application shown in FIG. 16 is equivalent to theJSDK application 147 which realizes the state transitions shown in FIG.8. The information related to the state transitions for being displayedon the state-transition indicating area 540 is included in theapplication information and accumulated in the database, and suchinformation is used in the state-transition indicating area 540.

If the edit button 520 in the application state transition screen 500 isdepressed, the application notification unit 415 sets the applicationstate transition screen 500 in the edit mode. At this time, in order toavoid unjust editing performed by an authorized user, userauthentication for checking a user code or an administrator code may beperformed.

FIG. 17 is a diagram showing an example of the application statetransition display screen in the edit mode. In FIG. 17, the elementswhich are essentially the same as corresponding elements in FIG. 16 aredesignated by the same reference numerals, and a description thereofwill be omitted.

Apparently, the application state transition display screen 500 a in theedit mode differs from the display screen of FIG. 16, only in that theedit button 520 is not displayed. Moreover, operation in the edit modewhich will be performed when the state button currently displayed on thestate-transition indicating area 540 is depressed is also different fromthat in the case of the display screen of FIG. 16.

For example, if the scan button 541 corresponding to the scan state isdepressed, the application generation unit 414 displays the screen(which will be called the state edit display screen) for allowing theuser to perform editing of the state corresponding to the selectedbutton, on the touch panel 311.

FIG. 18 is a diagram showing an example of the state edit displayscreen.

As shown in FIG. 18, the state edit display screen 600 comprises acurrent state name indicating area 610, a transition addition button620, a state change button 630, a state edit button 640, and a statelist display area 650.

The current state name indicating area 610 is an area where the statename of the state (current state) which is considered as the currentediting object is displayed. The transition addition button 620 is abutton for allowing the user to add a new transition from the currentstate.

The state change button 630 is a button for allowing the user to replacethe current state with a different state, for being set to thetransition position of the current state.

The state edit button 640 is a button for allowing the user to edit theinternal state transition of the current state. The state list displayarea 650 is an area where a list of the states that can be realized inthe multi-function peripheral 101 (i.e., a list of the functionalmodules installed in the multi-function peripheral 101) is displayed,and the buttons corresponding to the functional modules are arranged inthe display area 650.

However, concerning the state which does not become a result of statetransition from the current state, or the state which cannot be replacedfor the current state, graying out of the corresponding button isperformed and it is displayed (which is indicated by the dotted line inFIG. 18).

Determination as to whether the state concerned can become a result ofstate transition from the current state or not, or determination as towhether the state concerned can be replaced for the current state or notis carried out based on definition information, which indicates therelationship between the respective states, stored in the HDD 233beforehand. For example, in this definition information, a list of thestates which can become a result of the state transition from thecurrent state is defined for every state. Therefore, the applicationgeneration unit 414 retrieves the definition information-from the HDD233 by using the current state as a key, and determines whether thestate concerned can become a result of state transition from the currentstate, based on the result of the retrieval. Moreover, the applicationgeneration unit 414 retrieves the definition information from the HDD233 by using the state concerned (which is, in this case, theauthentication state) from which the current state changes, as a key,and determines whether the state concerned can be replaced for thecurrent state, based on the result of the retrieval.

It is not necessary to limit the states displayed in the state listdisplay area 650 to the states of the functional modules alreadyinstalled in the multi-function peripheral 101. For example, the stateof the functional module which is not installed but exists in thenetwork connected to the multi-function peripheral 101 or in therecording medium inserted in the multi-function peripheral 101 may beused instead. In this case, the collector 401 collects periodically andautomatically the information related to the functional module from theHDD 233, the memory card 235, the above-mentioned recording medium, orthe above-mentioned network, and accumulates the collected informationin the database in the HDD 233 so that the accumulated information ismanaged.

If the transition addition button 620 in the state edit display screen600 is depressed and any of the buttons of the state list display area650 is chosen, the application generation unit 414 displays on the touchpanel 311 the display screen (which is called the transition conditionsetting display screen) which allows the user to set the conditions oftransition from the current state to the state related to the chosenbutton.

FIG. 19 is a diagram showing an example of the transition conditionsetting display screen.

As shown in FIG. 19, the transition condition setting display screen 700comprises a source state name indicating area 710, a destination statename indicating area 720, a transition event setting area 730, a guardcondition setting area 740, and an end button 750.

The source state name indicating area 710 is an area where the name ofthe source state of the transition which is the editing object in thetransition condition setting display screen 700 is displayed. And thedestination state name indicating area 720 is an area where the name ofthe destination state of the transition which is the editing object inthe transition condition setting display screen 700 is displayed.

In the example of FIG. 19, the case in which the print state in thestate list display area 650 of FIG. 18 is chosen as the destinationstate is assumed. The transition event setting area 730 is an area forallowing the user to set the event which causes the state transitionfrom the source state to the destination state.

In the example of FIG. 19, the “end” is chosen. This indicates that itis set up such that a result of the state transition after the sourcestate (i.e., the scan state) is completed is the destination state.

The guard condition setting area 740 is an area for allowing the user toset up the guard conditions which do not generate the state transition(i.e., the conditions inhibiting occurrence of the state transition).For example, if “fatal error” is chosen, it means that the statetransition is not generated when a fatal error takes place.

In the example of FIG. 19, “none” is chosen. This indicates that it isset up that there are no guard conditions which inhibit occurrence ofthe transition from the scan state to the print state.

If the event and the guard conditions are set up and the end button 750is depressed, the application generation unit 414 generates a new JSDKapplication 147 based on the information related to the state transitionafter the editing. And the application generation unit 414 displays theapplication state transition display screen 500 a of the generated JSDKapplication 147.

FIG. 20 is a diagram showing an example of the application statetransition display screen where the edit result is reflected.

In FIG. 20, the elements which are the same as corresponding elements inFIG. 17 are designated by the same reference numerals, and a descriptionthereof will be omitted.

In the application state transition display screen 500 a of FIG. 20, aprint button 542 is added to the position located under the scan button541. That is, it is indicated that the print state is added as a resultof the transition from the scan state. This means that the statetransition which is equivalent to the state transition Z′′ shown in FIG.10 is added.

On the other hand, if the state edit button 640 in the state editdisplay screen 600 of FIG. 18 is depressed, the application generationunit 414 displays the screen (which will be called the functional modulestate-transition display screen) for allowing the user to edit the statetransition inside the functional module which performs the current state(the scan state in FIG. 18).

FIG. 21 is a diagram showing an example of the functional modulestate-transition display screen of the functional module.

As shown in FIG. 21, the functional module state-transition displayscreen 810 comprises a functional module name indicating area 811 and astate-transition indicating area 812. The functional module nameindicating area 811 is an area where the name of the functional module(the current functional module) which is the editing object, isdisplayed.

The state-transition indicating area 812 is an area where theinformation related to the state transition of the current functionalmodule is displayed. In the state-transition indicating area 812, thebuttons corresponding to the respective states are arranged in order ofthe state transition.

In the example of FIG. 21, the state transition related to the scanstate 503 in the state transition diagram of FIG. 8 is displayed.

It is possible to edit the state transition of the functional modulebased on the functional module state-transition display screen 810 ofFIG. 21, similar to the editing of the state transition of the JSDKapplication 147 mentioned above. For example, if the condition settingbutton 8121 in the state-transition indicating area 812 is depressed,the application generation unit 414 displays the state edit displayscreen by making the condition setting state (ready state) into theediting object.

FIG. 22 is a diagram showing an example of the state edit display screenwhich is related to the state of a functional module.

In the state edit display screen 820 of FIG. 22, a list of the buttonscorresponding to respective states which constitute the currentfunctional module is displayed.

For example, if the execution button 821 is chosen, the applicationgeneration unit 414 displays the transition condition setting displayscreen for allowing the user to set up the transition conditions whichmake the condition setting state into the source state and make theexecution state into the destination state.

FIG. 23 is a diagram showing an example of the transition conditionsetting display screen related to the internal state transition of afunctional module.

Since the operation method of the transition condition setting displayscreen 830 of FIG. 23 is essentially the same as that of the transitioncondition setting display screen 700 of FIG. 19, a description thereofwill be omitted.

If the authentication button 543, in the state-transition indicatingarea 540 of the application state transition screen 500 of FIG. 16 whichis not set in the edit mode, is depressed, the application generationunit 414 displays a detailed information setting display screen forallowing the user to set up a detailed information of the authenticationstate.

FIG. 24 is a diagram showing an example of the detailed informationsetting display screen. A specific unit for performing the userauthentication can be selected by the user in the detailed informationsetting screen 900 of FIG. 24.

As shown in FIG. 24, a user code, an ID card, a key counter, biometrics,etc. are displayed as alternatives. Graying out of the items of the IDcard, the key counter and the biometrics is performed except the usercode. This is because the functional modules for performing the userauthentication, other than that using the user code, have not been foundout.

The present invention is not limited to the above-described embodiments,and variations and modifications may be made without departing from thescope of the present invention.

Further, the present application is based on and claims the benefit ofpriority of Japanese patent application No. 2005-235422, filed on Aug.15, 2005, and Japanese patent application No. 2006-210268, filed on Aug.1, 2006, the entire contents of which are hereby incorporated byreference.

1. An information processing device adapted for performing anapplication program, comprising: a displaying unit causing a displaydevice to display information related to a state transition of theapplication program; and a generation unit receiving an input updatingrequest for updating information related to a displayed statetransition, and generating an application program which realizes a statetransition according to the updating request.
 2. The informationprocessing device according to claim 1 further comprising: a collectingunit collecting information related to an operating condition of theinformation processing device; and a detecting unit detecting arecommended application program for use in the information processingdevice by using the information collected by the collecting unit,wherein the displaying unit is configured to notify existence of theapplication program detected by the detecting unit as the recommendedapplication program for use in the information processing device, anddisplay the information related to the state transition of theapplication program on the display device.
 3. The information processingdevice according to claim 1 further comprising a collecting unitcollecting information related to an operating condition of theinformation processing device, wherein the generation unit is configuredto generate automatically a recommended application program for use inthe information processing device by using the information collected bythe collecting unit, and the displaying unit is configured to notifyexistence of the application program generated by the generation unit asthe recommended application program for use in the informationprocessing device, and display the information related to the statetransition of the application program on the display device.
 4. Theinformation processing device according to claim 2 wherein the detectingunit is configured to use the information collected by the collectingunit, on a user basis, and detect a recommended application program foruse in the information processing device on a user basis.
 5. Theinformation processing device according to claim 3 wherein thegeneration unit is configured to use the information collected by thecollecting unit, on a user basis, and generate a recommended applicationprogram for use in the information processing device on a user basis. 6.The information processing device according to claim 2 furthercomprising an acquisition unit acquiring information related to a statetransition of the information processing device by using the informationcollected by the collecting unit, wherein the detecting unit isconfigured to use the information acquired by the acquisition unit, anddetect a recommended application program for use in the informationprocessing device.
 7. The information processing device according toclaim 3 further comprising an acquisition unit acquiring informationrelated to a state transition of the information processing device byusing the information collected by the collecting unit, wherein thegeneration unit is configured to use the information acquired by theacquisition unit, and generate a recommended application program for usein the information processing device.
 8. The information processingdevice according to claim 6 wherein the detecting unit is configured touse the information acquired by the acquisition unit, on a user basis,and detect a recommended application program for use in the informationprocessing device on a user basis.
 9. The information processing deviceaccording to claim 7 wherein the generation unit is configured to usethe information acquired by the acquisition unit, on a user basis, andgenerate a recommended application program for use in the informationprocessing device on a user basis.
 10. An information processing methodfor an information processing device adapted for performing anapplication program, the method comprising the steps of: causing adisplay device to display information related to a state transition ofthe application program; receiving an input updating request forupdating information related to a displayed state transition; andgenerating an application program which realizes a state transitionaccording to the updating request.
 11. The information processing methodaccording to claim 10 further comprising the steps of: collectinginformation related to an operating condition of the informationprocessing device; and detecting a recommended application program foruse in the information processing device by using the collectedinformation, wherein the step of causing the display device isconfigured to notify existence of the detected application program asthe recommended application program for use in the informationprocessing device, and display the information related to the statetransition of the application program on the display device.
 12. Theinformation processing device according to claim 10 further comprisingthe steps of: collecting information related to an operating conditionof the information processing device; and generating automatically arecommended application program for use in the information processingdevice by using the collected information, wherein the step of causingthe display device is configured to notify existence of theautomatically generated application program as the recommendedapplication program for use in the information processing device, anddisplay the information related to the state transition of theapplication program on the display device.
 13. The informationprocessing method according to claim 11 further comprising the step ofacquiring information related to a state transition of the informationprocessing device by using the collected information, wherein the stepof detecting the recommended application program is configured to usethe acquired information.
 14. The information processing methodaccording to claim 12 further comprising the step of acquiringinformation related to a state transition of the information processingdevice by using the collected information, wherein the step ofgenerating automatically the recommended application program isconfigured to use the acquired information.
 15. A computer-readableprogram which, when executed by a computer, causes the computer toperform the information processing method according to claim
 10. 16. Acomputer-readable recording medium having program code stored thereonwhich, when executed by a computer, causes the computer to perform theinformation processing method according to claim 10.